The CICA Windows Explosion!/The CICA Windows Explosion! - Disc 1.iso/util/pfe0601.zip/FAQ.TXT

Text File | 1995-03-24 | 18KB | 422 lines

                         Frequently Asked Questions
                                     on
                          Programmer's File Editor
                         --------------------------

    [Answers in this file refer to facilities available in PFE 0.06.001]

    You may find information on any problem you have encountered in the
 problems.txt file, which lists known major problems in the current release

--

Q. What version of PFE is recommended for my current environments? I use
Windows 3.10, Windows NT and Windows 95

A. PFE is supplied in two forms: the 16-bit edition (PFE.EXE) and the
32-bit edition (PFE32.EXE). The recommended versions for various
platforms are these:

    Windows 3.1x            16-bit edition
    Windows NT 3.5            32-bit edition
    Windows 95            32-bit edition

Although the 32-bit edition should function on a Windows 3.1x system if
you have Win32s 1.20 installed, its use is not recommended. Some
functionality is not available, and the version is not extensively
tested in this mode

----

Q. How can I arrange that edit windows are created to use the maximum area
available in the MDI client area?

A. You can do this with the Options Preferences command. Start the
preferences dialog and select "Window Control" from the list of option
categories on the left. This shows you a panel that lets you configure
exactly how child windows will be created

----

Q. Why don't all the TrueType fonts I have installed on my system appear in the
printer and screen fonts dialogs?

A. Because PFE is a programming-oriented text editor, rather than a word
processor, it supports only fixed pitch fonts (ones in which all characters
occupy the same width on screen or paper). There are, sadly, very few fixed
pitch fonts available. There are no plans to add variable fixed pitch support
in a future release.

----

Q. How can I ensure that if I associate PFE with a file type in File Manager,
double clicking on a file of that type will bring up a new PFE window rather
than opening the file in an already-running instance?

A. Normally, whenever you start PFE, it will look to see if an instance is
already running. If it is, this instance is activated, and the names of any
files you give on the command line will be passed to it across a DDE link. If
you want to force a new instance of PFE to start instead of activating an
existing one, use the '/m' command line flag.

----

Q. I want PFE to remember the names of more than the last 5 files I've edited,
so I can pick them quickly from the File menu. How can I do this?

A. You can configure the Most Recently Used (MRU) list with the Options
Preferences command. Start the preferences dialog, and select "File
Menu" from the list of option categories on the left. This shows you the
panel that configures the MRU list.

You can configure the total size of the list, and how many files from
the list will appear on the File menu (you will be able to select from the
entire list with a dialog command that will follow the list on the menu).
You can also specify that the File menu should be drawn in two columns rather
than one if you want to show a large number of files. Note that you will need
to exit PFE and restart it before your changes take effect.

----

Q. I don't like the standard Windows File Manager, and prefer to use a third
party one. How can I get the File Manager item on the Execute menu to start
this instead of the standard one?

A. You can configure what the various "Manager" items on the Execute
menu do with the Options Preferences command. Start the preferences
dialog and select "Windows Managers" from the list of option categories
on the left to show the panel that handles this

For each of the menu items, you can specify that PFE should run either
the standard manager program supplied with Windows, or runs a command
line of your choice

----

Q. I use 4DOS-for-NT as my Windows/NT command processor instead of Microsoft's
cmd.exe - how can I get the Execute DOS Prompt and associated tool bar button to
start this?

A. Normally, PFE will use the executable file named in the COMSPEC
environment variable as the command processor. If this variable is not
set, it uses the standard defaults "command.com" under Windows 3.1x, and
"cmd.exe" under Windows NT

You can define the command processor you want to start with the Options
Preferences command. Start the preferences dialog and select "DOS
Shell" from the list of option categories on the left to show the
relevant panel, and define your preference

----

Q. What's the difference between the Execute Launch Application command and the
Execute Launch Windows Tool command?

A. In terms of what they accomplish - to start a Windows or a DOS application
running independently of PFE - there's none. Execute Launch Application starts
a dialog that prompts you for a command line; it remembers the last command
line you used, but that's all.

The Execute Launch Windows Tool command, by contrast, lets you define a whole
set of command lines, and label each one with a meaningful name. For example,
you could name a tool entry as "Edit Help File", and associate a command line
that runs Word for Windows to edit a file. Or you could have one called "Build
data file" that runs a DOS application with a set of files on its command line.
You just pick the function you want from your mnemonic list, without needing to
bother about what the command line has to be

----

Q. I use Windows NT on MIPS and DEC Alpha platforms - is there an executable
of PFE32 for these?

A. PFE32 exists only for Intel hardware. There are no plans for MIPS or DEC
Alpha versions

----

Q. How can I record my keyboard macros for use in other sessions?

A. This ability is not a part of the current PFE release. A future version will
include savable keyboard macros, implemented as editable macro libraries

----

Q. How does PFE manage to allow more than 32K of text to be edited in an edit
control?

A. PFE doesn't, in fact, use standard edit controls to show text. The windows
you see are ordinary MDI child windows, and the text is drawn explicitly by PFE
as required. Internally, a complicated memory management system keeps track of
where each line of each file is stored.

----

Q. Why, if I have word wrap switched on for a window, will PFE wrap text only
when I'm typing at the end of the line and not when I insert in the middle of
it?

A. The current design of PFE is set to do things that way for efficiency
reasons. A forthcoming release will feature a command to reflow the text of a
paragraph so that it fits within the wrap margin.

----

Q. Why do I get "Help file not found" when I ask for help?

A. Make sure that you have the help file pfe.hlp in the same directory as the
pfe.exe or pfe32.exe executable program

----

Q. Why is the default of 32 undoable actions so small? Surely, when I'm typing
text, I'll fill that up in 32 keypresses?

A. Actually, no - the undo system doesn't work in quite that way. It records
specific _actions_ in its stack, such as a drag-drop move of text, or a cut of
the highlighted text. When you're typing, each keypress is considered as part
of a _single_ action, which is terminated only when you do something different,
like moving the caret with the arrow keys, or switching to another window.

Then, when you use the Undo Typing command, PFE will remove all the typing
you've performed in that action (a future release of PFE will probably let you
undo typing actions character-by-character too)

You can change the number of undo actions that PFE records with the
Options Preferences command. Start the preferences dialog and select
"Editing Files" from the list of option categories on the left to show
the relevant panel that lets you set the size of the list

----

Q. If I select some text and start to drag it to a new location, how can I
change my mind without having to drop the text somewhere and then undo the
action?

A. You can cancel a drag-and-drop in one of two ways. If the highlighted text
is visible in the window, move the mouse cursor somewhere inside it and release
the left button. Alternatively, press the Escape key before you release the
left mouse button.

----

Q. How can I use drag-and-drop to move text from one window to another?

A. In the current design, PFE supports drag-and-drop only _within_ a window.
Inter-window operation may be added in a future release.

----

Q. How can I configure PFE so that the File Save command and its associated
tool bar button are always available? At the moment, I can only use the command
when I've changed the file in some way.

A. By default, PFE enables the File Save command only when the file showing in
a window has altered. This gives you some feedback (complementing the 'file
changed' marker in the status bar) that helps you avoid un-necessary saves.

You can use the Options Preferences command to change this setting.
Start the preferences dialog and select "Saving Files" from the list of
option categories on the left to show the relevant panel. Check the box
labelled "Allow File Save on unaltered files" to make the File Save
command and the toolbar button always available

----

Q. I like the window that runs DOS commands with output capture to start full
screen, and to have specific tuning details set. How can I do this?

A. DOS commands with output capture are run by either the $pfedos.exe (for
Windows 3) or $pfeds32.exe (for Windows/NT) helper modules. To change how the
windows are created, set up suitable PIF files $pfedos.pif and/or $pfeds32.pif
in the same directory, and use the Windows PIF editor to set the details as you
require

----

Q. How do I insert a Form Feed into a file, or specify it in the Find and
Replace dialogs?

A. To insert a Form Feed (or any other non-typable character) use the
EditTextInsertASCIICode command, which is by default mapped to Ctrl+Q. This
starts up a dialog that lets you select Esc and Ctrl+A - Ctrl+Z easily by name,
or specify any ASCII code you like as a number.

To specify Form Feed in the Find or Replace dialogs, write it as the two-
character sequence "\f". You can also specify end-of-line by "\n" and tab by
"\t"; and you can specify an arbitrary code as "\xhh", where "hh" represents
two hex digits. Remember that if you actually want a "\" character, you need to
write it as "\\".

----

Q. Why do I see lots of files with type .&&& (PFE version 0.05.006) or .$$$
(PFE version 0.05.007 and later) in my directories?

A. These are the backup files that PFE produces whenever you save a file. If a
file of the same name exists already, PFE renames it with a type of .$$$ before
writing the new data to disk.

The Options Preferences command allows you to configure some defaults
for how backup is handled. Start the preferences dialog and select "Backup"
from the list of option categories on the left to show the relevant
panel.

In this dialog, you can disable all backup permanently; choose to have
PFE make backup files to the same directory as the original file but
with a file extension of your choice; or to make the copy into a file of
the same name as the original, but in a subdirectory of the directory
containing it

The File Save As dialog and the Options Default Modes and Options
Current Modes dialogs also let you control some backup actions on a per-
file basis

----

Q. I am using the Italian version of Windows 3.1x, and when I use the
File Open command I can only specify the name of the file to open by
typing it in to the file name control at top left - selecting the name
by mouse from the list of files doesn't work

A. The various file opening dialogs are not controlled by PFE, but
instead are standard Windows features provided by Microsoft. The code
that creates the dialogs is held in a file called "commdlg.dll" which is
kept in your Windows system directory.

Some early versions of the Italian language commdlg.dll appear to have
bugs that affect the dialogs when used by PFE (and probably other
applications too). You should contact your supplier or your local Microsoft
company to obtain an up-to-date version of the commdlg.dll file.

----

Q. I used the Options Preferences, Options Default Modes and Options
Current Modes command to set background colours for my edit windows and
the main PFE workspace. Why are the colours I get not the ones I
selected?

A. Depending on what type of video adapter you have fitted to your
computer, only a very few of the infinite number of colours can be shown
as pure or "solid" colours. Normally your system will provide 16 such
solid colours, and you will see these in the block of colours shown at
top left in the colour selection dialog.

When Windows is asked to display some other colour, it has to use a
technique known as "dithering", that simulates the shade you want. For
example, it might produce a pale blue by drawing a fine grid of dark
blue lines on a white background; this will appear to be the colour you
wanted when seen from a suitable distance.

Dithered colours are very unpleasant to use as backgrounds for text, and
writing text on such a background is very much slower that if the
background were a solid colour. For these reasons, PFE does not support
the use of dithered colours, but instead translates the colour value you
select to the closest available solid colour.

----

Q. Does PFE run correctly under Windows NT 3.5 and Windows 95?

A. The 32-bit edition of PFE requires Windows NT 3.5 to run; it will not
work on Windows NT 3.1

The 32-bit edition has been tested on the Windows 95 M7 beta release and
works satisfactorily. Some functions do not yet have the normal Windows
95 look and feel, and integration into the Windows 95 shell is yet to be
done.

----

Q. I work with a number of large projects and would like to have
separate customised PFE environments. Can I do this?

A. You can use PFE's ability to locate its initialisation file pfe.ini
or pfe32.ini in arbitrary directories to do this.

Start the Options Preferences command, and select the "Startup" panel
from the list on the left. In the panel on the right, click the "In
startup directory" button.

PFE will now take its initialisation file from the directory it starts
in, so you can have specific Program Manager icons that start t in
directories specific to each individual project.

The default key map file pfe.key or pfe32.key is also looked for in this
directory, and perhaps you will want to do this. However, if you want to
have only one centralised key map file, you should use the "key Mapping"
panel of the Options Preferences dialog to set a specific path name for
the key map file that is independent of the initialisation directory.
This can, of course, be a path in your Windows directory.

--

Q. What are the licensing arrangements for PFE? I use it at home and
would like to do so at my work too.

A. PFE is FreeWare. You don't need to register to use it, and there is
no fee. You can use it at home, or at work without restriction.

If PFE provides functionality that is necessary for any software that
you are marketing (for example, it's necessary for users of your product
to have an editor that can cope with huge files) then you can obtain a
licence that will enable you to do this.

The help file contains full details on the current usage and licensing
position.

--

Q. I'm editing files on a NFS-mounted partition, and whenever I save my
edit changes the long name of the file disappears and all I see is the
NFS-generated 8.3 name. What's happened?

A. The problem is in the way that PFE makes backups when you save files.
In the current version, any existing file is renamed to be the backup
copy, and a new file is created with the old name to save the changes
into.

The step of renaming the file breaks the association that NFS maintains
between the DOS 8.3 name and the file's long name. Thus, when PFE
creates the new file to save - using the 8.3 name - NFS can no longer
translate this to the "real" name and so has to pass the 8.3 name itself
to Windows.

The only circumvention available in the current release is to disable
making backup copies in these circumstances.

--

Q. I'm using Windows NT on an Intel system and also on a PowerPC. The
PowerPC version of PFE does not think that keymap and template files I
made on the Intel version are valid. What's wrong?

A. For this release of PFE it was not possible to make the format of
.key and .tpl files the same between versions of the 32-bit edition for
different hardware platforms. This will be corrected in a forthcoming
release

--

Q. Why doesn't the 32-bit edition of PFE support long file names on my
NTFS and FAT partitions under Windows NT and Winbdows 95?

A. Actually, the 32-bit edition _does_ support long file names. The probable
reason that you think it doesn't has to do with a design flaw in the Microsoft
Common Dialogs - these are the standard dialogs that you see when you open and
save files.

The dialogs all date back to the first release Windows 3.10, long before
Windows NT. Microft designed them so that an application could - as PFE does -
allow multiple files to be selected in one go; in such cases the application is
given a list of filenames, separated by spaces.

The problem is that under NTFS the space character is a legal part of a file
name. The Common Dialog routines can't tell whether something with a space in
it is one file name containing a space, or two filenames that don't.

There is no solution to this other than to not use spaces as part of your long
file names.

--